Terminal requesting network slice capabilites from non-3GPP access network

ABSTRACT

Systems, methods, and instrumentalities are described for a wireless transmit/receive unit (WTRU), comprising a memory, and a processor to execute instructions from the memory, wherein the processor is configured to access a non-3rd Generation Partnership Project (3GPP) Access Network (AN), establish a link with a Non-3GPP Interworking Function (N3IWF) via the non-3GPP AN, request information from the N3IWF about network slicing capabilities of a 3GPP Radio Access Network (RAN), receive information from the N3IWF about network slicing capabilities of the 3GPP RAN, and determine whether to register with the 3GPP RAN based upon the network slicing capabilities of the 3GPP RAN. Systems, methods, and instrumentalities are described for sending information about network slicing capabilities of a 3GPP RAN to a N3IWF, establishing a link between a WTRU operating on a non-3GPP AN and the N3IWF via the non-3GPP AN, and sending information from the N3IWF to the WTRU about network slicing capabilities of the 3GPP RAN.

CROSS-REFERENCE TO RELATED APPLICATION

This application is the National Stage entry under 35 U.S.C. § 371 ofPatent Cooperation Treaty Application PCT/US2018/046747, filed Aug. 14,2018, which claims priority from U.S. Provisional Patent Application No.62/545,160, filed on Aug. 14, 2017, 2017, which is incorporated byreference herein in its entirety.

BACKGROUND

Mobile communications using wireless communication continue to evolve. Afifth generation may be referred to as 5G. A previous (legacy)generation of mobile communication may be, for example, fourthgeneration (4G) long term evolution (LTE).

SUMMARY

Systems, methods, and instrumentalities are disclosed for a wirelesstransmit/receive unit (WTRU), comprising a memory, and a processor toexecute instructions from the memory, wherein the processor isconfigured to access a non-3rd Generation Partnership Project (3GPP)Access Network (AN), establish a link with a Non-3GPP InterworkingFunction (N3IWF) via the non-3GPP AN, request information from the N3IWFabout network slicing capabilities of a 3GPP Radio Access Network (RAN),receive information from the N3IWF about network slicing capabilities ofthe 3GPP RAN, and determine whether to register with the 3GPP RAN basedupon the network slicing capabilities of the 3GPP RAN. Systems, methods,and instrumentalities are disclosed for sending information aboutnetwork slicing capabilities of a 3GPP RAN to a N3IWF, establishing alink between a WTRU operating on a non-3GPP AN and the N3IWF via thenon-3GPP AN, and sending information from the N3IWF to the WTRU aboutnetwork slicing capabilities of the 3GPP RAN, wherein the WTRUdetermines whether to register with the 3GPP RAN based upon the networkslicing capabilities of the 3GPP RAN.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a system diagram illustrating an example communicationssystem in which one or more disclosed embodiments may be implemented.

FIG. 1B is a system diagram illustrating an example wirelesstransmit/receive unit (WTRU) that may be used within the communicationssystem illustrated in FIG. 1A according to an embodiment.

FIG. 10 is a system diagram illustrating an example radio access network(RAN) and an example core network (CN) that may be used within thecommunications system illustrated in FIG. 1A according to an embodiment.

FIG. 1D is a system diagram illustrating a further example RAN and afurther example CN that may be used within the communications systemillustrated in FIG. 1A according to an embodiment.

FIG. 2 is an example of network slicing advertisement through untrustednon-3rd Generation Partnership Project (3GPP) access.

FIG. 3 is an example of network slicing advertisement about networkslices that may be available through untrusted non-3GPP access.

FIG. 4 is an example of network slicing advertisement about networkslices of other Public Land Mobile Networks (PLMNs).

FIG. 5 is an example of network slicing advertisement through non-3GPPaccess.

DETAILED DESCRIPTION

A detailed description of illustrative embodiments will now be describedwith reference to the various Figures. Although this descriptionprovides a detailed example of possible implementations, it should benoted that the details are intended to be exemplary and in no way limitthe scope of the application.

FIG. 1A is a diagram illustrating an example communications system 100in which one or more disclosed embodiments may be implemented. Thecommunications system 100 may be a multiple access system that providescontent, such as voice, data, video, messaging, broadcast, etc., tomultiple wireless users. The communications system 100 may enablemultiple wireless users to access such content through the sharing ofsystem resources, including wireless bandwidth. For example, thecommunications systems 100 may employ one or more channel accessmethods, such as code division multiple access (CDMA), time divisionmultiple access (TDMA), frequency division multiple access (FDMA),orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tailunique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM(UW-OFDM), resource block-filtered OFDM, filter bank multicarrier(FBMC), and the like.

As shown in FIG. 1A, the communications system 100 may include wirelesstransmit/receive units (WTRUs) 102 a, 102 b, 102 c, 102 d, a RAN104/113, a CN 106/115, a public switched telephone network (PSTN) 108,the Internet 110, and other networks 112, though it will be appreciatedthat the disclosed embodiments contemplate any number of WTRUs, basestations, networks, and/or network elements. Each of the WTRUs 102 a,102 b, 102 c, 102 d may be any type of device configured to operateand/or communicate in a wireless environment. By way of example, theWTRUs 102 a, 102 b, 102 c, 102 d, any of which may be referred to as a“station” and/or a “STA”, may be configured to transmit and/or receivewireless signals and may include a user equipment (UE), a mobilestation, a fixed or mobile subscriber unit, a subscription-based unit, apager, a cellular telephone, a personal digital assistant (PDA), asmartphone, a laptop, a netbook, a personal computer, a wireless sensor,a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watchor other wearable, a head-mounted display (HMD), a vehicle, a drone, amedical device and applications (e.g., remote surgery), an industrialdevice and applications (e.g., a robot and/or other wireless devicesoperating in an industrial and/or an automated processing chaincontexts), a consumer electronics device, a device operating oncommercial and/or industrial wireless networks, and the like. Any of theWTRUs 102 a, 102 b, 102 c and 102 d may be interchangeably referred toas a UE.

The communications systems 100 may also include a base station 114 aand/or a base station 114 b. Each of the base stations 114 a, 114 b maybe any type of device configured to wirelessly interface with at leastone of the WTRUs 102 a, 102 b, 102 c, 102 d to facilitate access to oneor more communication networks, such as the CN 106/115, the Internet110, and/or the other networks 112. By way of example, the base stations114 a, 114 b may be a base transceiver station (BTS), a Node-B, an eNodeB, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller,an access point (AP), a wireless router, and the like. While the basestations 114 a, 114 b are each depicted as a single element, it will beappreciated that the base stations 114 a, 114 b may include any numberof interconnected base stations and/or network elements.

The base station 114 a may be part of the RAN 104/113, which may alsoinclude other base stations and/or network elements (not shown), such asa base station controller (BSC), a radio network controller (RNC), relaynodes, etc. The base station 114 a and/or the base station 114 b may beconfigured to transmit and/or receive wireless signals on one or morecarrier frequencies, which may be referred to as a cell (not shown).These frequencies may be in licensed spectrum, unlicensed spectrum, or acombination of licensed and unlicensed spectrum. A cell may providecoverage for a wireless service to a specific geographical area that maybe relatively fixed or that may change over time. The cell may furtherbe divided into cell sectors. For example, the cell associated with thebase station 114 a may be divided into three sectors. Thus, in oneembodiment, the base station 114 a may include three transceivers, i.e.,one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and mayutilize multiple transceivers for each sector of the cell. For example,beamforming may be used to transmit and/or receive signals in desiredspatial directions.

The base stations 114 a, 114 b may communicate with one or more of theWTRUs 102 a, 102 b, 102 c, 102 d over an air interface 116, which may beany suitable wireless communication link (e.g., radio frequency (RF),microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet(UV), visible light, etc.). The air interface 116 may be establishedusing any suitable radio access technology (RAT).

More specifically, as noted above, the communications system 100 may bea multiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. Forexample, the base station 114 a in the RAN 104/113 and the WTRUs 102 a,102 b, 102 c may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA), whichmay establish the air interface 115/116/117 using wideband CDMA (WCDMA).WCDMA may include communication protocols such as High-Speed PacketAccess (HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-SpeedDownlink (DL) Packet Access (HSDPA) and/or High-Speed Uplink (UL) PacketAccess (HSUPA).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement a radio technology such as Evolved UMTS TerrestrialRadio Access (E-UTRA), which may establish the air interface 116 usingLong Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/orLTE-Advanced Pro (LTE-A Pro).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement a radio technology such as NR Radio Access, which mayestablish the air interface 116 using New Radio (NR).

In an embodiment, the base station 114 a and the WTRUs 102 a, 102 b, 102c may implement multiple radio access technologies. For example, thebase station 114 a and the WTRUs 102 a, 102 b, 102 c may implement LTEradio access and NR radio access together, for instance using dualconnectivity (DC) principles. Thus, the air interface utilized by WTRUs102 a, 102 b, 102 c may be characterized by multiple types of radioaccess technologies and/or transmissions sent to/from multiple types ofbase stations (e.g., a eNB and a gNB).

In other embodiments, the base station 114 a and the WTRUs 102 a, 102 b,102 c may implement radio technologies such as IEEE 802.11 (i.e.,Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperabilityfor Microwave Access (WiMAX)), CDMA2000, CDMA2000 1×, CDMA2000 EV-DO,Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), InterimStandard 856 (IS-856), Global System for Mobile communications (GSM),Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and thelike.

The base station 114 b in FIG. 1A may be a wireless router, Home Node B,Home eNode B, or access point, for example, and may utilize any suitableRAT for facilitating wireless connectivity in a localized area, such asa place of business, a home, a vehicle, a campus, an industrialfacility, an air corridor (e.g., for use by drones), a roadway, and thelike. In one embodiment, the base station 114 b and the WTRUs 102 c, 102d may implement a radio technology such as IEEE 802.11 to establish awireless local area network (WLAN). In an embodiment, the base station114 b and the WTRUs 102 c, 102 d may implement a radio technology suchas IEEE 802.15 to establish a wireless personal area network (WPAN). Inyet another embodiment, the base station 114 b and the WTRUs 102 c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE,LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. Asshown in FIG. 1A, the base station 114 b may have a direct connection tothe Internet 110. Thus, the base station 114 b may not be required toaccess the Internet 110 via the CN 106/115.

The RAN 104/113 may be in communication with the CN 106/115, which maybe any type of network configured to provide voice, data, applications,and/or voice over internet protocol (VoIP) services to one or more ofthe WTRUs 102 a, 102 b, 102 c, 102 d. The data may have varying qualityof service (QoS) requirements, such as differing throughputrequirements, latency requirements, error tolerance requirements,reliability requirements, data throughput requirements, mobilityrequirements, and the like. The CN 106/115 may provide call control,billing services, mobile location-based services, pre-paid calling,Internet connectivity, video distribution, etc., and/or performhigh-level security functions, such as user authentication. Although notshown in FIG. 1A, it will be appreciated that the RAN 104/113 and/or theCN 106/115 may be in direct or indirect communication with other RANsthat employ the same RAT as the RAN 104/113 or a different RAT. Forexample, in addition to being connected to the RAN 104/113, which may beutilizing a NR radio technology, the CN 106/115 may also be incommunication with another RAN (not shown) employing a GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

The CN 106/115 may also serve as a gateway for the WTRUs 102 a, 102 b,102 c, 102 d to access the PSTN 108, the Internet 110, and/or the othernetworks 112. The PSTN 108 may include circuit-switched telephonenetworks that provide plain old telephone service (POTS). The Internet110 may include a global system of interconnected computer networks anddevices that use common communication protocols, such as thetransmission control protocol (TCP), user datagram protocol (UDP) and/orthe internet protocol (IP) in the TCP/IP internet protocol suite. Thenetworks 112 may include wired and/or wireless communications networksowned and/or operated by other service providers. For example, thenetworks 112 may include another CN connected to one or more RANs, whichmay employ the same RAT as the RAN 104/113 or a different RAT.

Some or all of the WTRUs 102 a, 102 b, 102 c, 102 d in thecommunications system 100 may include multi-mode capabilities (e.g., theWTRUs 102 a, 102 b, 102 c, 102 d may include multiple transceivers forcommunicating with different wireless networks over different wirelesslinks). For example, the WTRU 102 c shown in FIG. 1A may be configuredto communicate with the base station 114 a, which may employ acellular-based radio technology, and with the base station 114 b, whichmay employ an IEEE 802 radio technology.

FIG. 1B is a system diagram illustrating an example WTRU 102. As shownin FIG. 1B, the WTRU 102 may include a processor 118, a transceiver 120,a transmit/receive element 122, a speaker/microphone 124, a keypad 126,a display/touchpad 128, non-removable memory 130, removable memory 132,a power source 134, a global positioning system (GPS) chipset 136,and/or other peripherals 138, among others. It will be appreciated thatthe WTRU 102 may include any sub-combination of the foregoing elementswhile remaining consistent with an embodiment.

The processor 118 may be a general purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs)circuits, any other type of integrated circuit (IC), a state machine,and the like. The processor 118 may perform signal coding, dataprocessing, power control, input/output processing, and/or any otherfunctionality that enables the WTRU 102 to operate in a wirelessenvironment. The processor 118 may be coupled to the transceiver 120,which may be coupled to the transmit/receive element 122. While FIG. 1Bdepicts the processor 118 and the transceiver 120 as separatecomponents, it will be appreciated that the processor 118 and thetransceiver 120 may be integrated together in an electronic package orchip.

The transmit/receive element 122 may be configured to transmit signalsto, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, thetransmit/receive element 122 may be an antenna configured to transmitand/or receive RF signals. In an embodiment, the transmit/receiveelement 122 may be an emitter/detector configured to transmit and/orreceive IR, UV, or visible light signals, for example. In yet anotherembodiment, the transmit/receive element 122 may be configured totransmit and/or receive both RF and light signals. It will beappreciated that the transmit/receive element 122 may be configured totransmit and/or receive any combination of wireless signals.

Although the transmit/receive element 122 is depicted in FIG. 1B as asingle element, the WTRU 102 may include any number of transmit/receiveelements 122. More specifically, the WTRU 102 may employ MIMOtechnology. Thus, in one embodiment, the WTRU 102 may include two ormore transmit/receive elements 122 (e.g., multiple antennas) fortransmitting and receiving wireless signals over the air interface 116.

The transceiver 120 may be configured to modulate the signals that areto be transmitted by the transmit/receive element 122 and to demodulatethe signals that are received by the transmit/receive element 122. Asnoted above, the WTRU 102 may have multi-mode capabilities. Thus, thetransceiver 120 may include multiple transceivers for enabling the WTRU102 to communicate via multiple RATs, such as NR and IEEE 802.11, forexample.

The processor 118 of the WTRU 102 may be coupled to, and may receiveuser input data from, the speaker/microphone 124, the keypad 126, and/orthe display/touchpad 128 (e.g., a liquid crystal display (LCD) displayunit or organic light-emitting diode (OLED) display unit). The processor118 may also output user data to the speaker/microphone 124, the keypad126, and/or the display/touchpad 128. In addition, the processor 118 mayaccess information from, and store data in, any type of suitable memory,such as the non-removable memory 130 and/or the removable memory 132.The non-removable memory 130 may include random-access memory (RAM),read-only memory (ROM), a hard disk, or any other type of memory storagedevice. The removable memory 132 may include a subscriber identitymodule (SIM) card, a memory stick, a secure digital (SD) memory card,and the like. In other embodiments, the processor 118 may accessinformation from, and store data in, memory that is not physicallylocated on the WTRU 102, such as on a server or a home computer (notshown).

The processor 118 may receive power from the power source 134, and maybe configured to distribute and/or control the power to the othercomponents in the WTRU 102. The power source 134 may be any suitabledevice for powering the WTRU 102. For example, the power source 134 mayinclude one or more dry cell batteries (e.g., nickel-cadmium (NiCd),nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion),etc.), solar cells, fuel cells, and the like.

The processor 118 may also be coupled to the GPS chipset 136, which maybe configured to provide location information (e.g., longitude andlatitude) regarding the current location of the WTRU 102. In additionto, or in lieu of, the information from the GPS chipset 136, the WTRU102 may receive location information over the air interface 116 from abase station (e.g., base stations 114 a, 114 b) and/or determine itslocation based on the timing of the signals being received from two ormore nearby base stations. It will be appreciated that the WTRU 102 mayacquire location information by way of any suitablelocation-determination method while remaining consistent with anembodiment.

The processor 118 may further be coupled to other peripherals 138, whichmay include one or more software and/or hardware modules that provideadditional features, functionality and/or wired or wirelessconnectivity. For example, the peripherals 138 may include anaccelerometer, an e-compass, a satellite transceiver, a digital camera(for photographs and/or video), a universal serial bus (USB) port, avibration device, a television transceiver, a hands free headset, aBluetooth® module, a frequency modulated (FM) radio unit, a digitalmusic player, a media player, a video game player module, an Internetbrowser, a Virtual Reality and/or Augmented Reality (VR/AR) device, anactivity tracker, and the like. The peripherals 138 may include one ormore sensors, the sensors may be one or more of a gyroscope, anaccelerometer, a hall effect sensor, a magnetometer, an orientationsensor, a proximity sensor, a temperature sensor, a time sensor; ageolocation sensor; an altimeter, a light sensor, a touch sensor, amagnetometer, a barometer, a gesture sensor, a biometric sensor, and/ora humidity sensor.

The WTRU 102 may include a full duplex radio for which transmission andreception of some or all of the signals (e.g., associated withparticular subframes for both the UL (e.g., for transmission) anddownlink (e.g., for reception) may be concurrent and/or simultaneous.The full duplex radio may include an interference management unit 139 toreduce and or substantially eliminate self-interference via eitherhardware (e.g., a choke) or signal processing via a processor (e.g., aseparate processor (not shown) or via processor 118). In an embodiment,the WRTU 102 may include a half-duplex radio for which transmission andreception of some or all of the signals (e.g., associated withparticular subframes for either the UL (e.g., for transmission) or thedownlink (e.g., for reception)).

FIG. 10 is a system diagram illustrating the RAN 104 and the CN 106according to an embodiment. As noted above, the RAN 104 may employ anE-UTRA radio technology to communicate with the WTRUs 102 a, 102 b, 102c over the air interface 116. The RAN 104 may also be in communicationwith the CN 106.

The RAN 104 may include eNode-Bs 160 a, 160 b, 160 c, though it will beappreciated that the RAN 104 may include any number of eNode-Bs whileremaining consistent with an embodiment. The eNode-Bs 160 a, 160 b, 160c may each include one or more transceivers for communicating with theWTRUs 102 a, 102 b, 102 c over the air interface 116. In one embodiment,the eNode-Bs 160 a, 160 b, 160 c may implement MIMO technology. Thus,the eNode-B 160 a, for example, may use multiple antennas to transmitwireless signals to, and/or receive wireless signals from, the WTRU 102a.

Each of the eNode-Bs 160 a, 160 b, 160 c may be associated with aparticular cell (not shown) and may be configured to handle radioresource management decisions, handover decisions, scheduling of usersin the UL and/or DL, and the like. As shown in FIG. 10, the eNode-Bs 160a, 160 b, 160 c may communicate with one another over an X2 interface.

The CN 106 shown in FIG. 10 may include a mobility management entity(MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN)gateway (or PGW) 166. While each of the foregoing elements is depictedas part of the CN 106, it will be appreciated that any of these elementsmay be owned and/or operated by an entity other than the CN operator.

The MME 162 may be connected to each of the eNode-Bs 162 a, 162 b, 162 cin the RAN 104 via an S1 interface and may serve as a control node. Forexample, the MME 162 may be responsible for authenticating users of theWTRUs 102 a, 102 b, 102 c, bearer activation/deactivation, selecting aparticular serving gateway during an initial attach of the WTRUs 102 a,102 b, 102 c, and the like. The MME 162 may provide a control planefunction for switching between the RAN 104 and other RANs (not shown)that employ other radio technologies, such as GSM and/or WCDMA.

The SGW 164 may be connected to each of the eNode Bs 160 a, 160 b, 160 cin the RAN 104 via the S1 interface. The SGW 164 may generally route andforward user data packets to/from the WTRUs 102 a, 102 b, 102 c. The SGW164 may perform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when DL data is available forthe WTRUs 102 a, 102 b, 102 c, managing and storing contexts of theWTRUs 102 a, 102 b, 102 c, and the like.

The SGW 164 may be connected to the PGW 166, which may provide the WTRUs102 a, 102 b, 102 c with access to packet-switched networks, such as theInternet 110, to facilitate communications between the WTRUs 102 a, 102b, 102 c and IP-enabled devices.

The CN 106 may facilitate communications with other networks. Forexample, the CN 106 may provide the WTRUs 102 a, 102 b, 102 c withaccess to circuit-switched networks, such as the PSTN 108, to facilitatecommunications between the WTRUs 102 a, 102 b, 102 c and traditionalland-line communications devices. For example, the CN 106 may include,or may communicate with, an IP gateway (e.g., an IP multimedia subsystem(IMS) server) that serves as an interface between the CN 106 and thePSTN 108. In addition, the CN 106 may provide the WTRUs 102 a, 102 b,102 c with access to the other networks 112, which may include otherwired and/or wireless networks that are owned and/or operated by otherservice providers.

Although the WTRU is described in FIGS. 1A-1D as a wireless terminal, itis contemplated that in certain representative embodiments that such aterminal may use (e.g., temporarily or permanently) wired communicationinterfaces with the communication network.

In representative embodiments, the other network 112 may be a WLAN.

A WLAN in Infrastructure Basic Service Set (BSS) mode may have an AccessPoint (AP) for the BSS and one or more stations (STAs) associated withthe AP. The AP may have an access or an interface to a DistributionSystem (DS) or another type of wired/wireless network that carriestraffic in to and/or out of the BSS. Traffic to STAs that originatesfrom outside the BSS may arrive through the AP and may be delivered tothe STAs. Traffic originating from STAs to destinations outside the BSSmay be sent to the AP to be delivered to respective destinations.Traffic between STAs within the BSS may be sent through the AP, forexample, where the source STA may send traffic to the AP and the AP maydeliver the traffic to the destination STA. The traffic between STAswithin a BSS may be considered and/or referred to as peer-to-peertraffic. The peer-to-peer traffic may be sent between (e.g., directlybetween) the source and destination STAs with a direct link setup (DLS).In certain representative embodiments, the DLS may use an 802.11e DLS oran 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS)mode may not have an AP, and the STAs (e.g., all of the STAs) within orusing the IBSS may communicate directly with each other. The IBSS modeof communication may sometimes be referred to herein as an “ad-hoc” modeof communication.

When using the 802.11ac infrastructure mode of operation or a similarmode of operations, the AP may transmit a beacon on a fixed channel,such as a primary channel. The primary channel may be a fixed width(e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.The primary channel may be the operating channel of the BSS and may beused by the STAs to establish a connection with the AP. In certainrepresentative embodiments, Carrier Sense Multiple Access with CollisionAvoidance (CSMA/CA) may be implemented, for example in in 802.11systems. For CSMA/CA, the STAs (e.g., every STA), including the AP, maysense the primary channel. If the primary channel is sensed/detectedand/or determined to be busy by a particular STA, the particular STA mayback off. One STA (e.g., only one station) may transmit at any giventime in a given BSS.

High Throughput (HT) STAs may use a 40 MHz wide channel forcommunication, for example, via a combination of the primary 20 MHzchannel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHzwide channel.

Very High Throughput (VHT) STAs may support 20 MHz, 40 MHz, 80 MHz,and/or 160 MHz wide channels. The 40 MHz, and/or 80 MHz, channels may beformed by combining contiguous 20 MHz channels. A 160 MHz channel may beformed by combining 8 contiguous 20 MHz channels, or by combining twonon-contiguous 80 MHz channels, which may be referred to as an 80+80configuration. For the 80+80 configuration, the data, after channelencoding, may be passed through a segment parser that may divide thedata into two streams. Inverse Fast Fourier Transform (IFFT) processing,and time domain processing, may be done on each stream separately. Thestreams may be mapped on to the two 80 MHz channels, and the data may betransmitted by a transmitting STA. At the receiver of the receiving STA,the above described operation for the 80+80 configuration may bereversed, and the combined data may be sent to the Medium Access Control(MAC).

Sub 1 GHz modes of operation are supported by 802.11af and 802.11ah. Thechannel operating bandwidths, and carriers, are reduced in 802.11af and802.11ah relative to those used in 802.11n, and 802.11ac. 802.11afsupports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space(TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and16 MHz bandwidths using non-TVWS spectrum. According to a representativeembodiment, 802.11ah may support Meter Type Control/Machine-TypeCommunications, such as MTC devices in a macro coverage area. MTCdevices may have certain capabilities, for example, limited capabilitiesincluding support for (e.g., only support for) certain and/or limitedbandwidths. The MTC devices may include a battery with a battery lifeabove a threshold (e.g., to maintain a very long battery life).

WLAN systems, which may support multiple channels, and channelbandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include achannel which may be designated as the primary channel. The primarychannel may have a bandwidth equal to the largest common operatingbandwidth supported by all STAs in the BSS. The bandwidth of the primarychannel may be set and/or limited by a STA, from among all STAs inoperating in a BSS, which supports the smallest bandwidth operatingmode. In the example of 802.11ah, the primary channel may be 1 MHz widefor STAs (e.g., MTC type devices) that support (e.g., only support) a 1MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.Carrier sensing and/or Network Allocation Vector (NAV) settings maydepend on the status of the primary channel. If the primary channel isbusy, for example, due to a STA (which supports only a 1 MHz operatingmode), transmitting to the AP, the entire available frequency bands maybe considered busy even though a majority of the frequency bands remainsidle and may be available.

In the United States, the available frequency bands, which may be usedby 802.11ah, are from 902 MHz to 928 MHz. In Korea, the availablefrequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the availablefrequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidthavailable for 802.11ah is 6 MHz to 26 MHz depending on the country code

FIG. 1D is a system diagram illustrating the RAN 113 and the CN 115according to an embodiment. As noted above, the RAN 113 may employ an NRradio technology to communicate with the WTRUs 102 a, 102 b, 102 c overthe air interface 116. The RAN 113 may also be in communication with theCN 115.

The RAN 113 may include gNBs 180 a, 180 b, 180 c, though it will beappreciated that the RAN 113 may include any number of gNBs whileremaining consistent with an embodiment. The gNBs 180 a, 180 b, 180 cmay each include one or more transceivers for communicating with theWTRUs 102 a, 102 b, 102 c over the air interface 116. In one embodiment,the gNBs 180 a, 180 b, 180 c may implement MIMO technology. For example,gNBs 180 a, 108 b may utilize beamforming to transmit signals to and/orreceive signals from the gNBs 180 a, 180 b, 180 c. Thus, the gNB 180 a,for example, may use multiple antennas to transmit wireless signals to,and/or receive wireless signals from, the WTRU 102 a. In an embodiment,the gNBs 180 a, 180 b, 180 c may implement carrier aggregationtechnology. For example, the gNB 180 a may transmit multiple componentcarriers to the WTRU 102 a (not shown). A subset of these componentcarriers may be on unlicensed spectrum while the remaining componentcarriers may be on licensed spectrum. In an embodiment, the gNBs 180 a,180 b, 180 c may implement Coordinated Multi-Point (CoMP) technology.For example, WTRU 102 a may receive coordinated transmissions from gNB180 a and gNB 180 b (and/or gNB 180 c).

The WTRUs 102 a, 102 b, 102 c may communicate with gNBs 180 a, 180 b,180 c using transmissions associated with a scalable numerology. Forexample, the OFDM symbol spacing and/or OFDM subcarrier spacing may varyfor different transmissions, different cells, and/or different portionsof the wireless transmission spectrum. The WTRUs 102 a, 102 b, 102 c maycommunicate with gNBs 180 a, 180 b, 180 c using subframe or transmissiontime intervals (TTIs) of various or scalable lengths (e.g., containingvarying number of OFDM symbols and/or lasting varying lengths ofabsolute time).

The gNBs 180 a, 180 b, 180 c may be configured to communicate with theWTRUs 102 a, 102 b, 102 c in a standalone configuration and/or anon-standalone configuration. In the standalone configuration, WTRUs 102a, 102 b, 102 c may communicate with gNBs 180 a, 180 b, 180 c withoutalso accessing other RANs (e.g., such as eNode-Bs 160 a, 160 b, 160 c).In the standalone configuration, WTRUs 102 a, 102 b, 102 c may utilizeone or more of gNBs 180 a, 180 b, 180 c as a mobility anchor point. Inthe standalone configuration, WTRUs 102 a, 102 b, 102 c may communicatewith gNBs 180 a, 180 b, 180 c using signals in an unlicensed band. In anon-standalone configuration WTRUs 102 a, 102 b, 102 c may communicatewith/connect to gNBs 180 a, 180 b, 180 c while also communicatingwith/connecting to another RAN such as eNode-Bs 160 a, 160 b, 160 c. Forexample, WTRUs 102 a, 102 b, 102 c may implement DC principles tocommunicate with one or more gNBs 180 a, 180 b, 180 c and one or moreeNode-Bs 160 a, 160 b, 160 c substantially simultaneously. In thenon-standalone configuration, eNode-Bs 160 a, 160 b, 160 c may serve asa mobility anchor for WTRUs 102 a, 102 b, 102 c and gNBs 180 a, 180 b,180 c may provide additional coverage and/or throughput for servicingWTRUs 102 a, 102 b, 102 c.

Each of the gNBs 180 a, 180 b, 180 c may be associated with a particularcell (not shown) and may be configured to handle radio resourcemanagement decisions, handover decisions, scheduling of users in the ULand/or DL, support of network slicing, dual connectivity, interworkingbetween NR and E-UTRA, routing of user plane data towards User PlaneFunction (UPF) 184 a, 184 b, routing of control plane informationtowards Access and Mobility Management Function (AMF) 182 a, 182 b andthe like. As shown in FIG. 1D, the gNBs 180 a, 180 b, 180 c maycommunicate with one another over an Xn interface.

The CN 115 shown in FIG. 1D may include at least one AMF 182 a, 182 b,at least one UPF 184 a,184 b, at least one Session Management Function(SMF) 183 a, 183 b, and possibly a Data Network (DN) 185 a, 185 b. Whileeach of the foregoing elements is depicted as part of the CN 115, itwill be appreciated that any of these elements may be owned and/oroperated by an entity other than the CN operator.

The AMF 182 a, 182 b may be connected to one or more of the gNBs 180 a,180 b, 180 c in the RAN 113 via an N2 interface and may serve as acontrol node. For example, the AMF 182 a, 182 b may be responsible forauthenticating users of the WTRUs 102 a, 102 b, 102 c, support fornetwork slicing (e.g., handling of different Protocol Data Unit (PDU)sessions with different requirements), selecting a particular SMF 183 a,183 b, management of the registration area, termination of NASsignaling, mobility management, and the like. Network slicing may beused by the AMF 182 a, 182 b in order to customize CN support for WTRUs102 a, 102 b, 102 c based on the types of services being utilized WTRUs102 a, 102 b, 102 c. For example, different network slices may beestablished for different use cases such as services relying onultra-reliable low latency (URLLC) access, services relying on enhancedmassive mobile broadband (eMBB) access, services for machine typecommunication (MTC) access, and/or the like. The AMF 162 may provide acontrol plane function for switching between the RAN 113 and other RANs(not shown) that employ other radio technologies, such as LTE, LTE-A,LTE-A Pro, and/or non-3GPP access technologies such as WiFi.

The SMF 183 a, 183 b may be connected to an AMF 182 a, 182 b in the CN115 via an N11 interface. The SMF 183 a, 183 b may also be connected toa UPF 184 a, 184 b in the CN 115 via an N4 interface. The SMF 183 a, 183b may select and control the UPF 184 a, 184 b and configure the routingof traffic through the UPF 184 a, 184 b. The SMF 183 a, 183 b mayperform other functions, such as managing and allocating UE IP address,managing PDU sessions, controlling policy enforcement and QoS, providingdownlink data notifications, and the like. A PDU session type may beIP-based, non-IP based, Ethernet-based, and the like.

The UPF 184 a, 184 b may be connected to one or more of the gNBs 180 a,180 b, 180 c in the RAN 113 via an N3 interface, which may provide theWTRUs 102 a, 102 b, 102 c with access to packet-switched networks, suchas the Internet 110, to facilitate communications between the WTRUs 102a, 102 b, 102 c and IP-enabled devices. The UPF 184, 184 b may performother functions, such as routing and forwarding packets, enforcing userplane policies, supporting multi-homed PDU sessions, handling user planeQoS, buffering downlink packets, providing mobility anchoring, and thelike.

The CN 115 may facilitate communications with other networks. Forexample, the CN 115 may include, or may communicate with, an IP gateway(e.g., an IP multimedia subsystem (IMS) server) that serves as aninterface between the CN 115 and the PSTN 108. In addition, the CN 115may provide the WTRUs 102 a, 102 b, 102 c with access to the othernetworks 112, which may include other wired and/or wireless networksthat are owned and/or operated by other service providers. In oneembodiment, the WTRUs 102 a, 102 b, 102 c may be connected to a localData Network (DN) 185 a, 185 b through the UPF 184 a, 184 b via the N3interface to the UPF 184 a, 184 b and an N6 interface between the UPF184 a, 184 b and the DN 185 a, 185 b.

In view of FIGS. 1A-1D, and the corresponding description of FIGS.1A-1D, one or more, or all, of the functions described herein withregard to one or more of: WTRU 102 a-d, Base Station 114 a-b, eNode-B160 a-c, MME 162, SGW 164, PGW 166, gNB 180 a-c, AMF 182 a-ab, UPF 184a-b, SMF 183 a-b, DN 185 a-b, and/or any other device(s) describedherein, may be performed by one or more emulation devices (not shown).The emulation devices may be one or more devices configured to emulateone or more, or all, of the functions described herein. For example, theemulation devices may be used to test other devices and/or to simulatenetwork and/or WTRU functions.

The emulation devices may be designed to implement one or more tests ofother devices in a lab environment and/or in an operator networkenvironment. For example, the one or more emulation devices may performthe one or more, or all, functions while being fully or partiallyimplemented and/or deployed as part of a wired and/or wirelesscommunication network in order to test other devices within thecommunication network. The one or more emulation devices may perform theone or more, or all, functions while being temporarilyimplemented/deployed as part of a wired and/or wireless communicationnetwork. The emulation device may be directly coupled to another devicefor purposes of testing and/or may performing testing using over-the-airwireless communications.

The one or more emulation devices may perform the one or more, includingall, functions while not being implemented/deployed as part of a wiredand/or wireless communication network. For example, the emulationdevices may be utilized in a testing scenario in a testing laboratoryand/or a non-deployed (e.g., testing) wired and/or wirelesscommunication network in order to implement testing of one or morecomponents. The one or more emulation devices may be test equipment.Direct RF coupling and/or wireless communications via RF circuitry(e.g., which may include one or more antennas) may be used by theemulation devices to transmit and/or receive data.

Fifth generation (5G) wireless communication systems may support diverseuse cases with different requirements using the same physicalinfrastructure. A 5G wireless communication system may be implemented,for example, using network slicing, which may virtually partition anetwork into multiple logical slices. A (e.g., each) slice may beassociated with (e.g., specific) network capabilities andcharacteristics that may cater to requirements of one or more use cases.Different WTRUs may be accessed and/or may be assigned different networkslices depending on their capabilities and requested services.

A (e.g., 5G) network may permit a WTRU (e.g., UE) to discover slicesthat may be supported by the network. In an example, a network slice ina 3rd Generation Partnership Project (3GPP) network may be identifiedwith a Single Network Slice Selection Assistance information (S-NSSAI).An S-NSSAI may comprise, for example, (i) a Slice/Service type (SST),which may refer to expected Network Slice behavior (e.g., in terms offeatures and services) and (ii) a Slice Differentiator (SD), which mayrefer to (e.g., optional) information that may complement Slice/Servicetype(s), e.g., to differentiate amongst multiple Network Slices of thesame Slice/Service type. Information regarding a network slice may begenerally referred to as NSSAI and/or S-NSSAI herein (and vice versa).There may be various types of NSSAI used for various purposes.

A WTRU may be configured to provide information to assist with selectionof an Access and Mobility Management Function (AMF), for example usingNSSAI.

A WTRU may be configured by a home Public Land Mobile Network (PLMN)with slicing information, e.g., with a Configured NSSAI per PLMN. AConfigured NSSAI may be PLMN-specific. A home PLMN (HPLMN) may indicateone or more applicable PLMN(s) for a (e.g., each) Configured NSSAI.

A WTRU may provide a Requested NSSAI to a network (e.g., uponregistration). A WTRU in a PLMN may (e.g., only) use S-NSSAIs that maybelong to a Configured NSSAI, if any, of that PLMN.

A WTRU may (e.g., upon successful completion of a WTRU's Registrationprocedure) obtain (e.g., from an AMF) an Allowed NSSAI for a PLMN, whichmay include one or more S-NSSAIs. S-NSSAIs may be valid for a currentRegistration Area (e.g., that a WTRU has registered with) that may beprovided by a serving AMF. Multiple S-NSSAIs may be used simultaneouslyby a WTRU. A received Allowed NSSAI may (e.g., from a WTRU perspective)overwrite a Configured NSSAI associated with a PLMN.

A WTRU may (e.g., during registration) include a Requested NSSAI atRadio Resource Control (RRC) Connection Establishment and in Non-AccessStratum (NAS) messages. A RAN may route NAS signaling between a WTRU andan AMF. An AMF may be selected, for example, using a Requested NSSAIthat may be obtained during RRC Connection Establishment. A RAN mayroute NAS signaling to an AMF from a set of default AMFs, for example,when the RAN may be unable to select an AMF based on a Requested NSSAI.

A WTRU may access a NextGen Core, for example, via non-3GPP access. ANon-3GPP Interworking Function (N3IWF) may provide or support one ormore of the following functions: (i) support IPsec tunnel establishmentwith a WTRU (e.g., N3IWF may terminate IKEv2/IPsec protocols with a WTRUover NWu and may relay over N2 information to authenticate a WTRU andauthorize its access to a 5G Core Network); (ii) termination of N2 andN3 interfaces to a 5G Core Network for Control-Plane and user-plane,respectively; (iii) relay uplink and downlink control-plane NAS (e.g.,N1) signaling between WTRU and AMF; (iv) handle N2 signaling from SMF(e.g., relayed by AMF) related to PDU sessions and QoS; (v) establishIPsec Security Association (IPsec SA) to support PDU Session traffic;(vi) relay uplink and downlink user-plane packets between WTRU and UPF(e.g., De-capsulation/Encapsulation of packets for IPSec and N3tunnelling); (vii) enforce QoS corresponding to N3 packet marking (e.g.,taking into account QoS requirements that may be associated with suchmarking received over N2); (viii) N3 user-plane packet marking in theuplink; (ix) local mobility anchor within untrusted non-3GPP accessnetworks (e.g., using IKEv2 Mobility and Multihoming Protocol (MOBIKE))and/or (x) support AMF selection. The N3IWF may be implemented as astandalone network node or server or may be co-located with one or moreother network functions or gateways.

N3IWF may be an interface between non-3GPP access and the 3GPP 5G CoreNetwork. The N3IWF might be an interface towards 3GPP RAN over an Xninterface.

NSSAI may be registration area specific. A WTRU may request or demanddifferent types of slices from a network. Selection of a set of networkslice instances for a WTRU in a 3GPP 5G network may be triggered, forexample, by the first AMF that may be contacted in a registrationprocedure, which may lead to a change in AMF. A (e.g., 5G) network mayprovide inter-working or coordination between cellular network and otherRATs, e.g., 3GPP and non-3GPP (e.g., WiFi). Cross-RATs network slicingcapability advertisement (e.g., notification of available slices) may beimplemented, for example, with coordination between 3GPP and non-3GPPaccess technologies. Registration Areas (e.g., a set of Tracking Areaswhere one or more WTRUs may be registered) may be (e.g., independently)assigned and distinct, e.g., as between 3GPP and Non-3GPP access. NSSAIsmay be Registration Area specific.

A WTRU attached to a non-3GPP access network may send a message to oneor more network entities (e.g., N3IWF) to determine what slices may beavailable in a 3GPP access network. A WTRU attached to a 3GPP networkmay acquire information relating to slice availability in a nearbynon-3GPP network by requesting such information from one or more networkentities (e.g., AMF). Network slicing capability (e.g., in a 3GPPnetwork) may be different among multiple PLMNs and/or amongst differentregistration areas. A RAN may (e.g., during RRC ConnectionEstablishment) route NAS signaling to an AMF from a set of default AMFs,for example, when the RAN may be unable to select an AMF based on aRequested NSSAI. In some instances, a WTRU may be unable (e.g., withoutgoing through a Registration procedure) to re-select AMF in other PLMNswhere desired network slices may be available.

WTRUs may obtain information about available network slices acrossdistinct Access Networks (e.g., to provide awareness of network sliceavailability on 3GPP access while connected to a non-3GPP access and/orvice versa).

Information may be advertised/broadcast (e.g., in 3GPP access stratum,for example using system information) about network slicing capabilitiesthat may be available at non-3GPP accesses.

N3IWF may provide information (e.g., during an association proceduresuch as through a Generic Advertisement Service (GAS)) about networkslicing capabilities that may be available at a 3GPP access.

A RAN may select a PLMN (e.g., and AMF) and/or a Registration Area thatmay be (e.g., is/are) capable of fulfilling network slicing requestsfrom a WTRU, for example, based on knowledge from the RAN about multiplesubscriptions of the WTRU.

A WTRU may be configured to request and/or receive network slicingadvertisement information (e.g., information about available networkslices for a 3GPP network), for example through non-3GPP accessnetworks.

A WTRU may acquire information regarding an Allowed NSSAI, for example,upon registration with a 3GPP access network.

N3IWF may be utilized, for example, to disseminate information regardingone or more network slices. A 3GPP RAN may, for example, (e.g.,periodically) exchange information (e.g., via interfaces such N2 and N3)with a N3IWF about network slicing capabilities. A RAN may have thisinformation, for example, since it may be responsible for AMF selectionduring WTRU registration. This may be similar to multiple base stationssharing network slicing information (e.g., over an Xn interface).Information exchange may (e.g., also) occur between base stations (e.g.,RAN) and N3IWF.

An N3IWF may convey information (e.g., acquired from a 3GPP RAN) to aWTRU, for example, over an IPsec tunnel (e.g., via IPv6 neighbordiscovery messages, over ICMP, over DHCP, etc.).

FIG. 2 is an example of network slicing advertisement through untrustednon-3GPP access. FIG. 2 shows an example of how a WTRU may decide toregister with a 3GPP RAN, for example, based on network slicinginformation that may be fetched from non-3GPP (e.g., WiFi) Access.

Example procedures are described with numeric references that do notlimit this example or other examples to a particular order or number ofactivities (e.g., communication messages, analyses, determinations,selections and/or other activities). Examples presented and otherexamples may be implemented with any number and order of proceduralactivities, which may be the same or different (e.g., additional and/oralternative) relative to activities presented in examples.

At 201, 201 a, 201 b, a 3GPP RAN may, for example, share (e.g.,periodically and/or aperiodically) its network slicing capabilities withan N3IWF. For example, at 201 a 3GPP RAN may inform a N3IWF of networkslicing capabilities by sharing slicing information, such as, forexample, Available NSSAI (e.g., a set of one or more S-NSSAI forslice(s) that are available). At 201 a, an AMF and a N3IWF may exchangenetwork slicing capabilities information (e.g., Available NSSAI). At 201b, an AMF and a 3GPP RAN may exchange network slicing capabilitiesinformation (e.g., Available NSSAI). At 201, 201 a, 201 b, informationmay be updated periodically. At 201, 201 a, 201 b, information may beupdated on a per-event basis. An N3IWF may, for example, store thisinformation. Information may be (e.g., regularly) updated, for example,using (e.g., periodic and/or aperiodic) incoming information (e.g., froma 3GPP RAN). A 5G CN may (e.g., also) update gNBs and a N3IWF withinformation, e.g., regarding neighboring ANs. Dynamic Xn and NG-C(N2TNL) interface Configuration procedures may (e.g., also) be used totransfer slicing capabilities, for example, between one or more gNBs andN3IWFs and/or between one or more 5G CNs and applicable ANs.

At 202, a WTRU may (e.g., as it is powered on), for example, initiallybe associated with a non-3GPP (e.g., WiFi) access point for services. At202 a, 202 b, Generic Advertisement Services (GAS) may be used, forexample, to retrieve slicing information.

At 203, a WTRU may, for example, establish an IPsec tunnel with anN3IWF, e.g., to receive information from the N3IWF. At 203 a, 203 b, 203c, a WTRU may, for example, use Extensible Authentication Protocol (EAP)to encapsulate slicing information between the WTRU and an N3IWF. Thismay be accomplished, for example, with a vendor-specific procedure thatmay use EAP packets with an “Expanded” type. In an example, avendor-specific EAP procedure may comprise EAP-LWA, which may use anexisting 3GPP vendor-id that may be registered with IANA (e.g., under anSMI Private Enterprise Code registry).

At 204, an N3IWF may, for example, relay 3GPP RAN network slicingcapability information (e.g., Available NSSAIs (e.g., a set of one ormore S-NSSAI for slice(s) that are available)) to a WTRU (e.g., via anestablished IPsec tunnel). An N3IWF may, for example, provide a list ofAvailable S-NSSAI on a per Registration Area basis. Relaying ofinformation may be periodic and/or aperiodic. In an example, (e.g.,aperiodic) relaying may be triggered, for example, by one or more of thefollowing: (i) an occurrence of one or more events; (ii) a request froma WTRU and/or (iii) a decision by a network.

Relaying of 3GPP RAN network slicing capability information may betriggered, for example, by one or more events. Examples of events thatmay trigger relaying may include, for example, one or more of thefollowing: (i) a WTRU may move (e.g., to a specific location); (ii) aWTRU battery and/or WTRU mobility may reach a certain level orthreshold; and/or (iii) a WiFi traffic level may reach a certain levelor threshold.

An N3IWF may obtain information relating to occurrence(s) of one or moreevents, for example, via one or more Application Programming Interfaces(APIs) that may be capable of extracting context information for WiFiradio access and a WTRU. Context information may be, for example, in avirtualized computing platform (e.g., as part of “services” in aMulti-Access Edge Computing (MEC) architecture).

Relaying of 3GPP RAN network slicing capability information may betriggered, for example, by a request from a WTRU. In an example, a WTRUmay send a request message to a WiFi Network, for example, when adesirable network slice may not be available. A request may betransported, for example, by IPv6 neighbor/router solicitations, DHCPrequests, etc.

Relaying of 3GPP RAN network slicing capability information may betriggered, for example, by a network. A network decision may be made,for example, based on context information for WiFi radio access and/orfor a WTRU. Context information may be extracted, for example, via oneor more APIs (e.g., in a virtualized computing platform). Contextinformation may be extracted, for example, as part of “services” inMulti-Access Edge Computing (MEC) architecture.

At 205, a WTRU may (e.g., based on received information), for example,find that a 3GPP RAN may provide one or more network slices that may fitits requirement better. A WTRU may (e.g., decide to) initiate aregistration process with a 3GPP RAN (e.g., using a requested NSSAI). Arequested NSSAI may be, for example, a subset of an available NSSAI(e.g., that may have been previously shared via an N3IWF). At 206, the3GPP RAN may select an AMF. At 207, the WTRU may provide the requestedNSSAI to the network.

Advertisement of network slicing capabilities may be available, forexample, at non-3GPP access. A WTRU may attach to a 3GPP access network(e.g., directly) after it is powered on. A WTRU may request a set ofnetwork slices (e.g., Requested NSSAI), for example, from a 3GPP network(e.g., during registration process). A 3GPP RAN may (e.g., also) provideinformation (e.g., available NSSAI) to a WTRU. A WTRU (e.g., withoutavailable information) may be unable to obtain information about anetwork slicing capability of a (e.g., nearby) non-3GPP network.Information exchange between a 3GPP RAN and an N3IWF may (e.g., also)cover network slicing capability. A non-3GPP access network (e.g., WiFi)may (e.g., periodically or aperiodically) provide information (e.g.,relating to its network slicing capabilities) to a 3GPP RAN (e.g., viaan N3IWF). A 3GPP RAN may become aware of the availability of requestedslices, for example, through an N3IWF, which may be reachable from thelocation of a WTRU (e.g., meeting end-to-end requirements of a slice). ARAN may, for example, embed information relating to network slicingcapability of at least one non-3GPP network (e.g., that may be near aWTRU) in none or more signals, such RRC-Connection-ReConfigurationmessages (e.g., during and/or after registration).

FIG. 3 is an example of network slicing advertisement about networkslices that may be available through untrusted non-3GPP access. FIG. 3shows an example procedure that a WTRU may use to obtain network slicinginformation of WiFi Access from 3GPP RAN.

In an example (e.g., at 301), a 3GPP RAN may (e.g., periodically oraperiodically) fetch network slicing capabilities of a WiFi accessnetwork from an N3IWF. In an example (e.g., at 301 a, 301 b), NScapabilities (e.g., Available NSSAI) of a node in a Registration Areamay be configured, for example, by a CN at an Access Network (AN) (e.g.,3GPP RAN/N3IWF).

At 302, a WTRU may (e.g., as the WTRU may power on), for example, searchfor 3GPP RAN base stations (e.g., gNBs), which may be implemented, forexample, based on received synchronization signals (e.g., PSS/SSS)and/or system information (e.g., MIB/SIBs). A WTRU may initiate anattachment process, for example, to commence network registration.

At 303, a 3GPP RAN may (e.g., during a registration process), forexample, transmit a message (e.g., for RRC connection setup). A messagemay comprise, for example, one or more of the following: (i) informationthat may relate to a network slicing capability of a non-3GPP accessnetwork and/or (ii) an N3IWF IP Address.

At 304, a WTRU may (e.g., based on received information), for example,determine that non-3GPP access may provide one or more network slicesthat may fit its requirement better. A WTRU may decide to initiateattachment to a corresponding non-3GPP access network.

One or more S-NSSAI from a (e.g., only one) PLMN may limit possibilitiesfor WTRUs (e.g., with multiple subscriptions) to find potential networkslices from other subscribed PLMNs. Different PLMNs may (e.g.,periodically and/or aperiodically) exchange information relating totheir available NSSAI. A RAN belonging to a first PLMN may provideinformation regarding its available NSSAI to a WTRU and may (e.g., also)provide information regarding available NSSAI of a second PLMN.

FIG. 4 is an example of network slicing advertisement regarding networkslices of other PLMNs.

In an example (e.g., as shown in FIG. 4), a 3GPP RAN may belong todifferent PLMNs. At 401, different PLMNs may, for example, (e.g.,periodically or aperiodically (e.g., as information changes)) exchangeinformation relating to their network slicing capabilities. In anexample, a CN may (e.g., also) be involved in an exchange of networkslicing capabilities.

At 402, a WTRU (e.g., subscribing to a first PLMN and a second PLMN) may(e.g., as it is powered on), for example, search for 3GPP RAN basestations (e.g., gNBs) for its one or more subscribed PLMNs. This may beimplemented, for example, based on received synchronization signals(e.g., PSS/SSS) and/or system information (e.g., MIB/SIBs). A WTRU mayinitiate an attachment process, for example, to commence networkregistration (e.g., with a first PLMN).

At 403, a RAN belonging to a first PLMN may (e.g., during a registrationprocess), for example, transmit a message (e.g., for RRC connectionsetup). A message may comprise, for example, one or more of thefollowing: (i) an Available-NSSAI of a RAN belonging to the first PLMNand/or (ii) an Available-NSSAI of a RAN belonging to the second PLMN.

At 404, a WTRU may (e.g., based on received information), for example,determine that a RAN belonging to the second PLMN may provide one ormore network slices that may fit its requirement better. The WTRU maydecide to initiate attachment to the RAN belonging to the second PLMN.

Systems, methods, and instrumentalities have been disclosed foradvertising and selecting network slices across multiple accesstechnologies (e.g., 3GPP and non-3GPP access) and multi-subscriberscenarios in 5G. WTRUs may, for example, obtain information aboutavailable network slices across distinct Access Networks, which may, forexample, provide awareness of network slice availability for 3GPP accesswhile connected to a non-3GPP access and vice versa. Information may beadvertised/broadcast (e.g., in 3GPP access stratum) about networkslicing capabilities that may be available at non-3GPP accesses. AnN3IWF may provide information (e.g., during an association procedure)about network slicing capabilities that may be available at a 3GPPaccess. A RAN may select a PLMN (e.g., and AMF) and/or a RegistrationArea that may be capable of fulfilling one or more network slicingrequests from a WTRU, e.g., based on knowledge from a RAN regardingmultiple subscriptions of the WTRU.

FIG. 5 is an example of network slicing advertisement through non-3GPPaccess. At 502, the WTRU may attach to a non-3GPP access network. At503, the 3GPP RAN may provide information to (e.g., share with) theN3IWF about network slicing capabilities. At 504, the WTRU may establisha secure link (e.g., IPSec tunnel) with the N3IWF via the non-3GPPaccess network. At 505, the WTRU may (e.g., prior to registering withthat 3GPP network) request slicing information for the 3GPP cellularnetwork from the N3IWF using the established secure link. At 506, theWTRU may receive the slicing information for the 3GPP cellular networkfrom the N3IWF. The WTRU may determine whether or not to register to the3GPP cellular network (e.g., based on the received slicing information).

The processes and instrumentalities described herein may apply in anycombination, may apply to other wireless technologies, and for otherservices.

A WTRU may refer to an identity of the physical device, or to the user'sidentity such as subscription related identities, e.g., MSISDN, SIP URI,etc. WTRU may refer to application-based identities, e.g., user namesthat may be used per application.

Each of the computing systems described herein may have one or morecomputer processors having memory that are configured with executableinstructions or hardware for accomplishing the functions describedherein including determining the parameters described herein and sendingand receiving messages between entities (e.g., WTRU and network) toaccomplish the described functions.

The processes described above may be implemented in a computer program,software, and/or firmware incorporated in a computer-readable medium forexecution by a computer and/or processor. Examples of computer-readablemedia include, but are not limited to, electronic signals (transmittedover wired and/or wireless connections) and/or computer-readable storagemedia. Examples of computer-readable storage media include, but are notlimited to, a read only memory (ROM), a random access memory (RAM), aregister, cache memory, semiconductor memory devices, magnetic mediasuch as, but not limited to, internal hard disks and removable disks,magneto-optical media, and/or optical media such as CD-ROM disks, and/ordigital versatile disks (DVDs). A processor in association with softwaremay be used to implement a radio frequency transceiver for use in aWTRU, terminal, base station, RNC, and/or any host computer.

What is claimed:
 1. A method, comprising: sending a first message, via afirst access network, to a node in a second access network, wherein thefirst message indicates that a wireless transmit/receive unit (WTRU)requests information about a network slicing capability of the secondaccess network, receiving a second message, via the first accessnetwork, from the node in the second access network, wherein the secondmessage indicates the network slicing capability of the second accessnetwork; and sending a third message to register the WTRU with thesecond access network based upon the network slicing capability of thesecond access network.
 2. The method of claim 1, wherein the secondaccess network is a 3rd Generation Partnership Project (3GPP) RadioAccess Network (RAN).
 3. The method of claim 1, wherein the first accessnetwork is a non-3GPP Access Network (AN).
 4. The method of claim 1,wherein the node in the second access network is a Non-3 GPPInterworking Function (N3IWF).
 5. The method of claim 1, wherein theWTRU receives the second message indicating the network slicingcapability of the first access network before the WTRU has registeredwith the first access network.
 6. The method of claim 1, furthercomprising advertising the information about the network slicingcapability of the second access network through the first accessnetwork.
 7. The method of claim 1, wherein the information about thenetwork slicing capability of the second access network is sent to thenode in the second access network periodically.
 8. The method of claim1, wherein the WTRU receives the second message indicating the networkslicing capability of the second access network via one or more of anIPsec tunnel, or Extensible Authentication Protocol (EAP) encapsulatedthe network slicing capability of the second access network.
 9. Themethod of claim 1, wherein the the network slicing capability includesSingle Network Slice Selection Assistance information (S-NSSAI) aboutone or more available slices in the second access network.
 10. Themethod of claim 9, wherein the S-NSSAI is based on a Registration Area.11. A wireless transmit/receive unit (WTRU), comprising: a memory; and aprocessor to execute instructions from the memory, wherein the processoris configured to: send a first message, via the first access network, toa node in a second access network, wherein the first message indicatesthe WTRU requests information about a network slicing capability of thesecond access network; receive a second message, via the first accessnetwork, from the node in the second access network, wherein the secondmessage indicates the network slicing capability of the second accessnetwork; and send a third message to register with the second accessnetwork based upon the network slicing capability of the second accessnetwork.
 12. The WTRU of claim 11, wherein the WTRU receives the secondmessage indicating the network slicing capability of the second accessnetwork before the WTRU has registered with the second access network.13. The WTRU of claim 11, wherein the second message indicating thenetwork slicing capability of the second access network has beenadvertised through the first access network.
 14. The WTRU of claim 11,wherein the WTRU receives the second message indicating the networkslicing capability of the second access network via an IPsec tunnel. 15.The WTRU of claim 11, wherein the second message indicating the networkslicing capability of the second access network is encapsulated usingExtensible Authentication Protocol (EAP).
 16. The WTRU of claim 11,wherein the network slicing capability includes Single Network SliceSelection Assistance information (S-NSSAI) about one or more availableslices in the second access network.
 17. The WTRU of claim 16, whereinthe S-NSSAI is based on a Registration Area.
 18. The WTRU of claim 16,wherein one or more of the WTRU's location, battery level, mobility,connectivity to the second access network, or request triggers receiptof the S-NSSAI.
 19. The WTRU of claim 11, wherein the first accessnetwork is a non-3GPP Access Network (AN) and wherein the second accessnetwork is a 3rd Generation Partnership Project (3GPP) Radio AccessNetwork (RAN).
 20. The WTRU of claim 11, wherein the node in the secondaccess network is a Non-3GPP Interworking Function (N3IWF).